Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2678247fdf21f0ff227bc2202bfa1e74e655e7dca206ea320d173f0807490f59

Tx prefix hash: 65d8cb83e67f419e890fba4d3a0db84667db813c3d58021c881be4bc886c4b1d
Tx public key: 0d3e9c36c5ac5877db77b1736e901d78a6ef8b4b1133a7bf755365ef053197ca
Timestamp: 1752503272 Timestamp [UCT]: 2025-07-14 14:27:52 Age [y:d:h:m:s]: 00:178:19:05:14
Block: 1325372 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126583 RingCT/type: yes/0
Extra: 010d3e9c36c5ac5877db77b1736e901d78a6ef8b4b1133a7bf755365ef053197ca021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b28fcb6d0b89bc4ee533734a7c4641937dbcb27be8fdc9bdee6e6357dfe5b083 0.600000000000 1813117 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": 1325382, "vin": [ { "gen": { "height": 1325372 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b28fcb6d0b89bc4ee533734a7c4641937dbcb27be8fdc9bdee6e6357dfe5b083" } } ], "extra": [ 1, 13, 62, 156, 54, 197, 172, 88, 119, 219, 119, 177, 115, 110, 144, 29, 120, 166, 239, 139, 75, 17, 51, 167, 191, 117, 83, 101, 239, 5, 49, 151, 202, 2, 17, 0, 0, 0, 1, 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