Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 140b9d6d900cf2dfdddff5801eead8c23e23739e06e79051e0cf90ee8a54a92d

Tx prefix hash: 17c81572e4007ef82efc9efcb5ff1a5da0db7dccedf122e9c2eb3c48957a1b61
Tx public key: a0cb3eaf82838c690b21f06426c88b4dad9ff9bdaaf3af7a866023f031ba8546
Timestamp: 1721152801 Timestamp [UCT]: 2024-07-16 18:00:01 Age [y:d:h:m:s]: 00:222:01:34:07
Block: 1067133 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158571 RingCT/type: yes/0
Extra: 01a0cb3eaf82838c690b21f06426c88b4dad9ff9bdaaf3af7a866023f031ba85460211000000015ff1157f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33b3c703f2b8a6d59b12b31d3e1aa5ce269057b118fb5749ce7cf66cd1f25ba9 0.600000000000 1537860 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": 1067143, "vin": [ { "gen": { "height": 1067133 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33b3c703f2b8a6d59b12b31d3e1aa5ce269057b118fb5749ce7cf66cd1f25ba9" } } ], "extra": [ 1, 160, 203, 62, 175, 130, 131, 140, 105, 11, 33, 240, 100, 38, 200, 139, 77, 173, 159, 249, 189, 170, 243, 175, 122, 134, 96, 35, 240, 49, 186, 133, 70, 2, 17, 0, 0, 0, 1, 95, 241, 21, 127, 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