Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d08d5204fdbf7fe3c60f87545296b5ed15ebdc5e644fc963fc850f14f7b69d6c

Tx prefix hash: 139fb0f72ff3137e666a64a1f52f064997e51b562425b4aefacbb6529f077a88
Tx public key: 6b6f19b4a3ba4d93f2bd475093cfff48074d46c3199de54aff4c1475586d2dd0
Timestamp: 1711342524 Timestamp [UCT]: 2024-03-25 04:55:24 Age [y:d:h:m:s]: 01:049:09:32:53
Block: 985801 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 296280 RingCT/type: yes/0
Extra: 016b6f19b4a3ba4d93f2bd475093cfff48074d46c3199de54aff4c1475586d2dd002110000000759dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2b3c0c643502acf917d4a8ac5b79c72276c6dcc9a84f36f901faa0afff4900e0 0.600000000000 1446020 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": 985811, "vin": [ { "gen": { "height": 985801 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2b3c0c643502acf917d4a8ac5b79c72276c6dcc9a84f36f901faa0afff4900e0" } } ], "extra": [ 1, 107, 111, 25, 180, 163, 186, 77, 147, 242, 189, 71, 80, 147, 207, 255, 72, 7, 77, 70, 195, 25, 157, 229, 74, 255, 76, 20, 117, 88, 109, 45, 208, 2, 17, 0, 0, 0, 7, 89, 218, 211, 245, 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