Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ede803faf614cc14e37343fa8ba99b8ad29e2f91f6cbf4d5c071be57a0a638e7

Tx prefix hash: bf6aa5f2996d5fc9c5010a77a4ee5a4edc929d45177a043981fe0cd962976702
Tx public key: f1e9cacff1ce643aa5ec43236103df8fed302579869d7b2d5237569e193d9af7
Timestamp: 1754325839 Timestamp [UCT]: 2025-08-04 16:43:59 Age [y:d:h:m:s]: 00:101:17:30:36
Block: 1340207 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 71673 RingCT/type: yes/0
Extra: 01f1e9cacff1ce643aa5ec43236103df8fed302579869d7b2d5237569e193d9af702110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f3678cdd1353814b390b356ceb70af64fa1769da82a953e2b63fe6c7480850f6 0.600000000000 1828024 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": 1340217, "vin": [ { "gen": { "height": 1340207 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f3678cdd1353814b390b356ceb70af64fa1769da82a953e2b63fe6c7480850f6" } } ], "extra": [ 1, 241, 233, 202, 207, 241, 206, 100, 58, 165, 236, 67, 35, 97, 3, 223, 143, 237, 48, 37, 121, 134, 157, 123, 45, 82, 55, 86, 158, 25, 61, 154, 247, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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