Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea8292fe93a7147a54a158febde764487db95603ce803f1daf802e4dcaacb3dc

Tx prefix hash: 96a35f20f2255e8f4cc8a2f7e2835f85a625eace12e9177f94a81ca0c4bec52f
Tx public key: 3781047cec23eb3e4218422b882ae4535ceaaa237f53e473ca6f277a535233c2
Timestamp: 1714118294 Timestamp [UCT]: 2024-04-26 07:58:14 Age [y:d:h:m:s]: 00:203:02:33:40
Block: 1008795 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 145391 RingCT/type: yes/0
Extra: 013781047cec23eb3e4218422b882ae4535ceaaa237f53e473ca6f277a535233c202110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ac32b5a867f33e1c4fe0d04115089f5573d91c55f38881b93cc9c3357a5fd913 0.600000000000 1470273 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": 1008805, "vin": [ { "gen": { "height": 1008795 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ac32b5a867f33e1c4fe0d04115089f5573d91c55f38881b93cc9c3357a5fd913" } } ], "extra": [ 1, 55, 129, 4, 124, 236, 35, 235, 62, 66, 24, 66, 43, 136, 42, 228, 83, 92, 234, 170, 35, 127, 83, 228, 115, 202, 111, 39, 122, 83, 82, 51, 194, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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