Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 4a14687a9a8cd7e9507f1a30f5a0753388abebea048cb9027133d8f797aaccd6

Tx prefix hash: 79891743e0f4156363b7c3aa44f687e59b3fe2752c78e918f303ab7f3970f2c7
Tx public key: 608882ddfa0d0e5275a488e55da2c0a8e65ff8dbf12479afd6ebfe98f9857c39
Timestamp: 1734910165 Timestamp [UCT]: 2024-12-22 23:29:25 Age [y:d:h:m:s]: 00:108:13:12:03
Block: 1181081 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77341 RingCT/type: yes/0
Extra: 01608882ddfa0d0e5275a488e55da2c0a8e65ff8dbf12479afd6ebfe98f9857c39021100000006007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 975a882ee1c14f44f24559f7196874558f51f43538a06610fcbc219456480fb0 0.600000000000 1667496 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1181091, "vin": [ { "gen": { "height": 1181081 } } ], "vout": [ { "amount": 600000000, "target": { "key": "975a882ee1c14f44f24559f7196874558f51f43538a06610fcbc219456480fb0" } } ], "extra": [ 1, 96, 136, 130, 221, 250, 13, 14, 82, 117, 164, 136, 229, 93, 162, 192, 168, 230, 95, 248, 219, 241, 36, 121, 175, 214, 235, 254, 152, 249, 133, 124, 57, 2, 17, 0, 0, 0, 6, 0, 127, 151, 138, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8