Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e4dd51e4760869d000c2d8646a630c69bf227310afff943edb1f7646d7fc602c

Tx prefix hash: 171942cc39dba1ef552eaa39053ee6e538945b28bf47664574fa3af8beb513e8
Tx public key: 54026e5e79d0c211d29a3cb822e04cdb83cb08a661dfcb42bd8b3d916606c72d
Timestamp: 1737990776 Timestamp [UCT]: 2025-01-27 15:12:56 Age [y:d:h:m:s]: 00:328:04:07:27
Block: 1206303 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232335 RingCT/type: yes/0
Extra: 0154026e5e79d0c211d29a3cb822e04cdb83cb08a661dfcb42bd8b3d916606c72d021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3d627688cfafb64d3777e47f5bf99c26ac24d3d7c384f850834c8083fb5bc74 0.600000000000 1693006 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": 1206313, "vin": [ { "gen": { "height": 1206303 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3d627688cfafb64d3777e47f5bf99c26ac24d3d7c384f850834c8083fb5bc74" } } ], "extra": [ 1, 84, 2, 110, 94, 121, 208, 194, 17, 210, 154, 60, 184, 34, 224, 76, 219, 131, 203, 8, 166, 97, 223, 203, 66, 189, 139, 61, 145, 102, 6, 199, 45, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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