Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9e1b9556b31e6800ef054c3396236019deb7f8f3749928d9dd9c2acde8a0cb9

Tx prefix hash: 2d677e3fd7f92ca2bc1542a73184dda1ed1e7c58d3dc98176fb3478304e74920
Tx public key: 7e1bb74eec0aaa5d516455f3d3b0724b5ed9b60d98e6b32e28ddf8b5a66d5be5
Timestamp: 1731372637 Timestamp [UCT]: 2024-11-12 00:50:37 Age [y:d:h:m:s]: 00:045:12:58:58
Block: 1151744 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32587 RingCT/type: yes/0
Extra: 017e1bb74eec0aaa5d516455f3d3b0724b5ed9b60d98e6b32e28ddf8b5a66d5be5021100000003007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b4e70cdefa197f6bb5a9f4de1587dcba21e1ad699a9c865279aeab424774f31 0.600000000000 1637325 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": 1151754, "vin": [ { "gen": { "height": 1151744 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b4e70cdefa197f6bb5a9f4de1587dcba21e1ad699a9c865279aeab424774f31" } } ], "extra": [ 1, 126, 27, 183, 78, 236, 10, 170, 93, 81, 100, 85, 243, 211, 176, 114, 75, 94, 217, 182, 13, 152, 230, 179, 46, 40, 221, 248, 181, 166, 109, 91, 229, 2, 17, 0, 0, 0, 3, 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