Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4f0bdb357256520c99d4057f74798998068523f0d33db3a46ba30ee0dd02659

Tx prefix hash: 52c4c21389a5bd7ace7a0ff37581254f0ce6ae0c4a81f8c98261ebcd41ba0232
Tx public key: f6d174e75e4e77ffb19a7fc846b3f3bbd790aa526a54c2f139b0ad13fc940160
Timestamp: 1710713303 Timestamp [UCT]: 2024-03-17 22:08:23 Age [y:d:h:m:s]: 00:342:08:29:54
Block: 980586 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 244730 RingCT/type: yes/0
Extra: 01f6d174e75e4e77ffb19a7fc846b3f3bbd790aa526a54c2f139b0ad13fc94016002110000000859dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cb3cef8020716fa890f32a846d7adb8c51d31710cd922a59d9f357b68cab6104 0.600000000000 1440661 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": 980596, "vin": [ { "gen": { "height": 980586 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cb3cef8020716fa890f32a846d7adb8c51d31710cd922a59d9f357b68cab6104" } } ], "extra": [ 1, 246, 209, 116, 231, 94, 78, 119, 255, 177, 154, 127, 200, 70, 179, 243, 187, 215, 144, 170, 82, 106, 84, 194, 241, 57, 176, 173, 19, 252, 148, 1, 96, 2, 17, 0, 0, 0, 8, 89, 218, 211, 245, 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