Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7c72c7612ef99b550380d1f681841435aa17b7d96be61632f8a2fe5ec166302

Tx prefix hash: 57403770d9b6a77f2b6180d4bc105d691c22919f8e77747e00663a83a5d0c75a
Tx public key: b613a8788b96210c79052936df16f50d7718babb13b937ed9c3ea6a6f138383f
Timestamp: 1733368616 Timestamp [UCT]: 2024-12-05 03:16:56 Age [y:d:h:m:s]: 00:115:07:41:55
Block: 1168287 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82208 RingCT/type: yes/0
Extra: 01b613a8788b96210c79052936df16f50d7718babb13b937ed9c3ea6a6f138383f0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0a6c9079f9de1eaf532d783eb053f91049e17fb8b8715084cea2fedccb9fa5c1 0.600000000000 1653996 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": 1168297, "vin": [ { "gen": { "height": 1168287 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0a6c9079f9de1eaf532d783eb053f91049e17fb8b8715084cea2fedccb9fa5c1" } } ], "extra": [ 1, 182, 19, 168, 120, 139, 150, 33, 12, 121, 5, 41, 54, 223, 22, 245, 13, 119, 24, 186, 187, 19, 185, 55, 237, 156, 62, 166, 166, 241, 56, 56, 63, 2, 17, 0, 0, 0, 5, 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