Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 435c604c153c43e6b43954c6c359408d6b8685d52a442e1d3497f949b180f4d8

Tx prefix hash: d9c7760e251a93dcf834f74442d4103b428157cb1923dbc076cbd118fa413e7c
Tx public key: ba559655d5e7fa14bf33c6c378b98615f4c8ee0a91968d8e530989f45530c3c9
Timestamp: 1747741903 Timestamp [UCT]: 2025-05-20 11:51:43 Age [y:d:h:m:s]: 00:177:03:57:11
Block: 1287011 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124312 RingCT/type: yes/0
Extra: 01ba559655d5e7fa14bf33c6c378b98615f4c8ee0a91968d8e530989f45530c3c90211000000029f9fe68c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8374c4f6e4d401cd5c8cc5f088b7252c8913db4d156c4aa82eb996b60c1697a4 0.600000000000 1774478 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": 1287021, "vin": [ { "gen": { "height": 1287011 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8374c4f6e4d401cd5c8cc5f088b7252c8913db4d156c4aa82eb996b60c1697a4" } } ], "extra": [ 1, 186, 85, 150, 85, 213, 231, 250, 20, 191, 51, 198, 195, 120, 185, 134, 21, 244, 200, 238, 10, 145, 150, 141, 142, 83, 9, 137, 244, 85, 48, 195, 201, 2, 17, 0, 0, 0, 2, 159, 159, 230, 140, 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