Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8497cc1478e3eccd25985e74c2315ddef69a5931e4ad7c451b3d33113455de72

Tx prefix hash: d4aad5a0dc6f896f62aa49c4b4a8c12d04f8d0a1c9840684c643c2088b46e634
Tx public key: f7f3e96f995d1d0c388c45b2ef3d7198ce16f6a3659fa1fdb0d0547381092dcb
Timestamp: 1633523414 Timestamp [UCT]: 2021-10-06 12:30:14 Age [y:d:h:m:s]: 03:055:08:36:57
Block: 347848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 816671 RingCT/type: yes/0
Extra: 01f7f3e96f995d1d0c388c45b2ef3d7198ce16f6a3659fa1fdb0d0547381092dcb021100000001f29d7abf000000000000000000

1 output(s) for total of 43.195211371000 dcy

stealth address amount amount idx
00: 85561a6cd59d1cc0eca2e51082c58119cdaf7a58e5cad49dd38dadda7e030f91 43.195211371000 712606 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": 347858, "vin": [ { "gen": { "height": 347848 } } ], "vout": [ { "amount": 43195211371, "target": { "key": "85561a6cd59d1cc0eca2e51082c58119cdaf7a58e5cad49dd38dadda7e030f91" } } ], "extra": [ 1, 247, 243, 233, 111, 153, 93, 29, 12, 56, 140, 69, 178, 239, 61, 113, 152, 206, 22, 246, 163, 101, 159, 161, 253, 176, 208, 84, 115, 129, 9, 45, 203, 2, 17, 0, 0, 0, 1, 242, 157, 122, 191, 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