Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f9da6913d1e10924fc71f403c58e405c0e52e24c1a85bbe418af0f0f28e4b39c

Tx prefix hash: 82d340cecd22708d2572b74e099845a86826289fe3e2453c25f7c495fdd855c8
Tx public key: 6c8bdafd05b6cf3520fea9557d38e5031a57918274dc6b4708829abaec8ef9fe
Timestamp: 1697365030 Timestamp [UCT]: 2023-10-15 10:17:10 Age [y:d:h:m:s]: 01:151:05:20:07
Block: 870101 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 369116 RingCT/type: yes/0
Extra: 016c8bdafd05b6cf3520fea9557d38e5031a57918274dc6b4708829abaec8ef9fe02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.803515425000 dcy

stealth address amount amount idx
00: 9adca829f30bfd667f2175f9eecc71c910e3841f9bb67f5925606376b5463f7e 0.803515425000 1324974 of 0

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": 870111, "vin": [ { "gen": { "height": 870101 } } ], "vout": [ { "amount": 803515425, "target": { "key": "9adca829f30bfd667f2175f9eecc71c910e3841f9bb67f5925606376b5463f7e" } } ], "extra": [ 1, 108, 139, 218, 253, 5, 182, 207, 53, 32, 254, 169, 85, 125, 56, 229, 3, 26, 87, 145, 130, 116, 220, 107, 71, 8, 130, 154, 186, 236, 142, 249, 254, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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