Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e132700d8ce003c87f9e5888da4bb5fc4fc36a1ac821a716fc3a7af53dd752d2

Tx prefix hash: 5875bcb365233ecc3f89dee3b40e1239b72fcdfdea2d65378b6e52ed840e381d
Tx public key: e6f200e74c9ea05637665f7fe5ac6d2f1522fd7066e9a8fc4b0098ca18c14e4f
Timestamp: 1763627395 Timestamp [UCT]: 2025-11-20 08:29:55 Age [y:d:h:m:s]: 00:033:19:57:28
Block: 1416117 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 24222 RingCT/type: yes/0
Extra: 01e6f200e74c9ea05637665f7fe5ac6d2f1522fd7066e9a8fc4b0098ca18c14e4f02110000000a70609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2706ed557792ee21a3c8bf59ab6e8e063454b127fe3200662cf9d823c39f9e2b 0.600000000000 1904636 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": 1416127, "vin": [ { "gen": { "height": 1416117 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2706ed557792ee21a3c8bf59ab6e8e063454b127fe3200662cf9d823c39f9e2b" } } ], "extra": [ 1, 230, 242, 0, 231, 76, 158, 160, 86, 55, 102, 95, 127, 229, 172, 109, 47, 21, 34, 253, 112, 102, 233, 168, 252, 75, 0, 152, 202, 24, 193, 78, 79, 2, 17, 0, 0, 0, 10, 112, 96, 157, 3, 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