Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2375c0c135b137c77a38f5f14c952b6b06f67d864cb20666a62b1e6eae930be1

Tx prefix hash: 53be674106c94ad5b23fe5ebcde1cada286a44403a3cfa1d0f2fba73a222545f
Tx public key: 062a3c5bbf9deb6ae5cad166ce5944c3eb354da376542470651079f094620a12
Timestamp: 1730557967 Timestamp [UCT]: 2024-11-02 14:32:47 Age [y:d:h:m:s]: 00:150:07:17:18
Block: 1145000 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107247 RingCT/type: yes/0
Extra: 01062a3c5bbf9deb6ae5cad166ce5944c3eb354da376542470651079f094620a120211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a97efa25f5d2ff208dd65bd2f3e5a93c685bbf0370b1bf51cd0318183c251b9d 0.600000000000 1629357 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": 1145010, "vin": [ { "gen": { "height": 1145000 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a97efa25f5d2ff208dd65bd2f3e5a93c685bbf0370b1bf51cd0318183c251b9d" } } ], "extra": [ 1, 6, 42, 60, 91, 191, 157, 235, 106, 229, 202, 209, 102, 206, 89, 68, 195, 235, 53, 77, 163, 118, 84, 36, 112, 101, 16, 121, 240, 148, 98, 10, 18, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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