Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6005dcc9f54c72e5f8a3e789b8df2f7ba61500d4039ae19ed779f6279039cddf

Tx prefix hash: cba41733363a434541854962f149dcfb94e8a3842de22e527159ea5cf9a59f7f
Tx public key: 354f86e5897ab21b995d00c3ac85fb09c3bb3a40bba8f6d6766c530f6e927c64
Timestamp: 1741601934 Timestamp [UCT]: 2025-03-10 10:18:54 Age [y:d:h:m:s]: 00:255:22:29:03
Block: 1236194 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180634 RingCT/type: yes/0
Extra: 01354f86e5897ab21b995d00c3ac85fb09c3bb3a40bba8f6d6766c530f6e927c640211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bb073302e738800d6a69d3aee495bdb64059d8499300efbf4c80e054bdf1a75d 0.600000000000 1723139 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": 1236204, "vin": [ { "gen": { "height": 1236194 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bb073302e738800d6a69d3aee495bdb64059d8499300efbf4c80e054bdf1a75d" } } ], "extra": [ 1, 53, 79, 134, 229, 137, 122, 178, 27, 153, 93, 0, 195, 172, 133, 251, 9, 195, 187, 58, 64, 187, 168, 246, 214, 118, 108, 83, 15, 110, 146, 124, 100, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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