Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3ab25b2a5535f1f5d503bf10fd498e77259dbfc64c0a6944777ef5df57976f6

Tx prefix hash: 444bedf08e619b394837cfa71c674dabdfd419ed9c0b2b9229ffc67fbce97ee0
Tx public key: f81f31b43e7349e1235af24e4145346608fa3f929de218b3177c247b83e3d6c6
Timestamp: 1736406573 Timestamp [UCT]: 2025-01-09 07:09:33 Age [y:d:h:m:s]: 00:112:22:42:25
Block: 1193434 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80520 RingCT/type: yes/0
Extra: 01f81f31b43e7349e1235af24e4145346608fa3f929de218b3177c247b83e3d6c60211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad9e5e634f0b339a75b96b12b21063200f60e8c2577c22f764844fd525e4f4c2 0.600000000000 1679995 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": 1193444, "vin": [ { "gen": { "height": 1193434 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad9e5e634f0b339a75b96b12b21063200f60e8c2577c22f764844fd525e4f4c2" } } ], "extra": [ 1, 248, 31, 49, 180, 62, 115, 73, 225, 35, 90, 242, 78, 65, 69, 52, 102, 8, 250, 63, 146, 157, 226, 24, 179, 23, 124, 36, 123, 131, 227, 214, 198, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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