Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 01317e7789463cd929990518db53b81028a88e5773b0b02839fbd6b471f282a1

Tx prefix hash: cd314ff070699cb6a95bbcee9526e78e43536aaf05f37e1de672ad6b78c4066f
Tx public key: 3a40d57412007cf31694bda2ba7d8077ea4f73f9d24904d8ff4a23d20b62440d
Timestamp: 1745788161 Timestamp [UCT]: 2025-04-27 21:09:21 Age [y:d:h:m:s]: 00:010:12:05:50
Block: 1270842 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7507 RingCT/type: yes/0
Extra: 013a40d57412007cf31694bda2ba7d8077ea4f73f9d24904d8ff4a23d20b62440d02110000000601491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b7b3238a8c7fbbe79ac888a843f254b845c89d9ded2a5c7dc59a3ecb1a912ec 0.600000000000 1758087 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": 1270852, "vin": [ { "gen": { "height": 1270842 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b7b3238a8c7fbbe79ac888a843f254b845c89d9ded2a5c7dc59a3ecb1a912ec" } } ], "extra": [ 1, 58, 64, 213, 116, 18, 0, 124, 243, 22, 148, 189, 162, 186, 125, 128, 119, 234, 79, 115, 249, 210, 73, 4, 216, 255, 74, 35, 210, 11, 98, 68, 13, 2, 17, 0, 0, 0, 6, 1, 73, 31, 136, 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