Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e7931c8ea70385d5e047f5ee57db50e512a0fd968fc9f3390407fbbda4b7c09a

Tx prefix hash: e61ee4fc4847e4e8f5b472de3a950bfaacf979cedc31d8bb3d90aefeef8b72eb
Tx public key: 3f933dbe4873be042460297bbb79dc0c1f33fcc68a6ec54d14369ed96f52d388
Timestamp: 1735079507 Timestamp [UCT]: 2024-12-24 22:31:47 Age [y:d:h:m:s]: 00:095:09:29:20
Block: 1182458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67951 RingCT/type: yes/0
Extra: 013f933dbe4873be042460297bbb79dc0c1f33fcc68a6ec54d14369ed96f52d3880211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b8464a638b93fdeea94a6a77903e7e9bcf6f0287e313c75c54ba70fcfa236482 0.600000000000 1668893 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": 1182468, "vin": [ { "gen": { "height": 1182458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b8464a638b93fdeea94a6a77903e7e9bcf6f0287e313c75c54ba70fcfa236482" } } ], "extra": [ 1, 63, 147, 61, 190, 72, 115, 190, 4, 36, 96, 41, 123, 187, 121, 220, 12, 31, 51, 252, 198, 138, 110, 197, 77, 20, 54, 158, 217, 111, 82, 211, 136, 2, 17, 0, 0, 0, 3, 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