Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d9da57d1ba33ff1ed7d9d8633fcc06a98b8b791a3aadf3173cd485da94730281

Tx prefix hash: 1d6189a0f3b7c576ea2ae2575c3f306af21e2a3d4e0305e4e5925753254b1d82
Tx public key: 9e7038b0e16d01ab596e2e8965f26a14950b8e6610cf3b5ed6d3e4407ff28442
Timestamp: 1728409679 Timestamp [UCT]: 2024-10-08 17:47:59 Age [y:d:h:m:s]: 00:170:07:20:32
Block: 1127277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 121498 RingCT/type: yes/0
Extra: 019e7038b0e16d01ab596e2e8965f26a14950b8e6610cf3b5ed6d3e4407ff28442021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3baa530fe75308e4a73afd5c2edbd444df48043de1aefc2e8f692ee60213e57b 0.600000000000 1610078 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": 1127287, "vin": [ { "gen": { "height": 1127277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3baa530fe75308e4a73afd5c2edbd444df48043de1aefc2e8f692ee60213e57b" } } ], "extra": [ 1, 158, 112, 56, 176, 225, 109, 1, 171, 89, 110, 46, 137, 101, 242, 106, 20, 149, 11, 142, 102, 16, 207, 59, 94, 214, 211, 228, 64, 127, 242, 132, 66, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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