Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3be91b013b33859c314ed24692ca0fe6ac7a63a81dd2d9b868ebd36defb8a47c

Tx prefix hash: ef5c3a34b6104e035ff4dd3f32bdb80289b39b96e3114048fc721014f3f800a9
Tx public key: 962cf353f9830f6846673b7b18c0958373dfe1a9ac1ec835afb3b5e7dab5a0a2
Timestamp: 1730910405 Timestamp [UCT]: 2024-11-06 16:26:45 Age [y:d:h:m:s]: 00:187:13:48:52
Block: 1147924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133909 RingCT/type: yes/0
Extra: 01962cf353f9830f6846673b7b18c0958373dfe1a9ac1ec835afb3b5e7dab5a0a2021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 12cbbfe8d3ad89ba927e85e2fb83f391b07fc11ee64c75449a08f171a59b5705 0.600000000000 1632639 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": 1147934, "vin": [ { "gen": { "height": 1147924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "12cbbfe8d3ad89ba927e85e2fb83f391b07fc11ee64c75449a08f171a59b5705" } } ], "extra": [ 1, 150, 44, 243, 83, 249, 131, 15, 104, 70, 103, 59, 123, 24, 192, 149, 131, 115, 223, 225, 169, 172, 30, 200, 53, 175, 179, 181, 231, 218, 181, 160, 162, 2, 17, 0, 0, 0, 3, 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