Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 11db3dc16306f9b74be2b5c77a38da779b753a4a5c2fa66a0bd3208bda57bd7a

Tx prefix hash: 5399fe9cb61822cd8e066756c9d4d21f37eeec6019d0da6892f07eafd91e2da1
Tx public key: 42f8b18bf9aeb4f0e0355ae830d047475bbb3d3548b38df75b1fc022d2e66327
Timestamp: 1712690406 Timestamp [UCT]: 2024-04-09 19:20:06 Age [y:d:h:m:s]: 00:363:13:30:21
Block: 996931 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 259932 RingCT/type: yes/0
Extra: 0142f8b18bf9aeb4f0e0355ae830d047475bbb3d3548b38df75b1fc022d2e66327021100000001bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d0dda2a53977d139db1e76ff5e175e419b96eafb13caac6d2e1790df3006347f 0.600000000000 1457359 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": 996941, "vin": [ { "gen": { "height": 996931 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d0dda2a53977d139db1e76ff5e175e419b96eafb13caac6d2e1790df3006347f" } } ], "extra": [ 1, 66, 248, 177, 139, 249, 174, 180, 240, 224, 53, 90, 232, 48, 208, 71, 71, 91, 187, 61, 53, 72, 179, 141, 247, 91, 31, 192, 34, 210, 230, 99, 39, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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