Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fb4df95acca47c9ce62630357f01a2dc51a95d6a7534ac475162586a3c3483d

Tx prefix hash: c09e85627fdda69b546d3d84e81584549ddbf1d5d1b691a93574aa34e4ea0008
Tx public key: 0c28192293ed92569c53e7c2d40eb0572bc96d01b29c7a7472c4f70e28d31290
Timestamp: 1735646685 Timestamp [UCT]: 2024-12-31 12:04:45 Age [y:d:h:m:s]: 00:076:00:24:43
Block: 1187139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 54130 RingCT/type: yes/0
Extra: 010c28192293ed92569c53e7c2d40eb0572bc96d01b29c7a7472c4f70e28d31290021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9398f4bc35317da5f12a4044ebb6f3f78cda57fa6bf21e0a6aca05840e782d32 0.600000000000 1673626 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": 1187149, "vin": [ { "gen": { "height": 1187139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9398f4bc35317da5f12a4044ebb6f3f78cda57fa6bf21e0a6aca05840e782d32" } } ], "extra": [ 1, 12, 40, 25, 34, 147, 237, 146, 86, 156, 83, 231, 194, 212, 14, 176, 87, 43, 201, 109, 1, 178, 156, 122, 116, 114, 196, 247, 14, 40, 211, 18, 144, 2, 17, 0, 0, 0, 4, 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