Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d963f008deaa2441e885d97654366ed928191d481ce6c6367846857e24f85830

Tx prefix hash: b3300b29a92dac6fd5f21723ab0c657b5a58c6a0fbc17994ecb95181110d20b2
Tx public key: adf14f923a6d4dde9d3aca9dc852e613b0284589acc0e0cb9294df316ba5b20a
Timestamp: 1578241285 Timestamp [UCT]: 2020-01-05 16:21:25 Age [y:d:h:m:s]: 04:326:03:26:22
Block: 39311 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1122308 RingCT/type: yes/0
Extra: 01adf14f923a6d4dde9d3aca9dc852e613b0284589acc0e0cb9294df316ba5b20a021100000005d81c26c0000000000000000000

1 output(s) for total of 454.731117873000 dcy

stealth address amount amount idx
00: c3f35dca8d3a488dfce4ce2924e7294fc5786a556540c9acb37c2fbd2b9c5ecd 454.731117873000 67695 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": 39321, "vin": [ { "gen": { "height": 39311 } } ], "vout": [ { "amount": 454731117873, "target": { "key": "c3f35dca8d3a488dfce4ce2924e7294fc5786a556540c9acb37c2fbd2b9c5ecd" } } ], "extra": [ 1, 173, 241, 79, 146, 58, 109, 77, 222, 157, 58, 202, 157, 200, 82, 230, 19, 176, 40, 69, 137, 172, 192, 224, 203, 146, 148, 223, 49, 107, 165, 178, 10, 2, 17, 0, 0, 0, 5, 216, 28, 38, 192, 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