Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f6ee5eaeddde9e1261bcc4e8ee97518bd4ebd794ddb9ad827c78ecc6f5533a7

Tx prefix hash: 0ec42f0aa67de0af55d8370e5e68e973f44840715314d5f45f7988138a80ee9b
Tx public key: 34df799f74c31a6120f864a3a3e070294c57292d262049b5dcb04aa796e43c0d
Timestamp: 1734750651 Timestamp [UCT]: 2024-12-21 03:10:51 Age [y:d:h:m:s]: 00:018:22:37:02
Block: 1179752 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13528 RingCT/type: yes/0
Extra: 0134df799f74c31a6120f864a3a3e070294c57292d262049b5dcb04aa796e43c0d0211000000051f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc24946898abbfc8718bd5301ebd7fbd8b676d33ca01a3536d61ac589cf20920 0.600000000000 1666151 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": 1179762, "vin": [ { "gen": { "height": 1179752 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc24946898abbfc8718bd5301ebd7fbd8b676d33ca01a3536d61ac589cf20920" } } ], "extra": [ 1, 52, 223, 121, 159, 116, 195, 26, 97, 32, 248, 100, 163, 163, 224, 112, 41, 76, 87, 41, 45, 38, 32, 73, 181, 220, 176, 74, 167, 150, 228, 60, 13, 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