Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5edc9df5fbeb542e4f58aa58de79cae97b1edf7548ca96cb5a2908623fc29ae

Tx prefix hash: dc032faab8eeb8e32275c7c4c4ff8192636cafbc5a90fa09d255752b07982c9b
Tx public key: 88f5f9407b5559e90358bb498756ccb4ca9aaf9578d6750212cee4b78ae952e1
Timestamp: 1765641330 Timestamp [UCT]: 2025-12-13 15:55:30 Age [y:d:h:m:s]: 00:012:05:17:34
Block: 1432808 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 8747 RingCT/type: yes/0
Extra: 0188f5f9407b5559e90358bb498756ccb4ca9aaf9578d6750212cee4b78ae952e102110000000270609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 00ef18fed143a5124f915b4aea7b2d3a7fdba4d237bf2ec19b1f6cc8738f9fd3 0.600000000000 1921587 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": 1432818, "vin": [ { "gen": { "height": 1432808 } } ], "vout": [ { "amount": 600000000, "target": { "key": "00ef18fed143a5124f915b4aea7b2d3a7fdba4d237bf2ec19b1f6cc8738f9fd3" } } ], "extra": [ 1, 136, 245, 249, 64, 123, 85, 89, 233, 3, 88, 187, 73, 135, 86, 204, 180, 202, 154, 175, 149, 120, 214, 117, 2, 18, 206, 228, 183, 138, 233, 82, 225, 2, 17, 0, 0, 0, 2, 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