Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d17e00c31a895ba27b3dbe4bf6b9baa150d44442ea7d512a1b26684c1ba8849c

Tx prefix hash: 27b27eade0d291e4c881875ef7a04dd1a42d0fb6268aca9840741d4e31de4839
Tx public key: 2aa985a5740eb828de4b644d18c8388934ea733cf8645c77182a3a0f0e9169e4
Timestamp: 1709242951 Timestamp [UCT]: 2024-02-29 21:42:31 Age [y:d:h:m:s]: 01:254:19:36:00
Block: 968381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 440840 RingCT/type: yes/0
Extra: 012aa985a5740eb828de4b644d18c8388934ea733cf8645c77182a3a0f0e9169e402110000000349a185bb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c8c89cd3754d9c5c433e216a48df3f5593960e1b5580920a60ba9be7924c091f 0.600000000000 1428196 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": 968391, "vin": [ { "gen": { "height": 968381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c8c89cd3754d9c5c433e216a48df3f5593960e1b5580920a60ba9be7924c091f" } } ], "extra": [ 1, 42, 169, 133, 165, 116, 14, 184, 40, 222, 75, 100, 77, 24, 200, 56, 137, 52, 234, 115, 60, 248, 100, 92, 119, 24, 42, 58, 15, 14, 145, 105, 228, 2, 17, 0, 0, 0, 3, 73, 161, 133, 187, 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