Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 454e33a2c4192357ff4a14673ab65fd1273e89dc8c9851aa0bea8fbeb11a5410

Tx prefix hash: e363d42790301f4e728c5f8783af487a0720481103d33adc4a727326002171c0
Tx public key: 4789bde49e8b198951da9c1a5cdbe9ff7232eaa3d2c26aaae1badddfd2c003b9
Timestamp: 1700152306 Timestamp [UCT]: 2023-11-16 16:31:46 Age [y:d:h:m:s]: 02:004:18:19:54
Block: 893013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 523172 RingCT/type: yes/0
Extra: 014789bde49e8b198951da9c1a5cdbe9ff7232eaa3d2c26aaae1badddfd2c003b9021100000001c5452960000000000000000000

1 output(s) for total of 0.674647969000 dcy

stealth address amount amount idx
00: 4a4936c66de8cfb6b06a783df0eb7caafadf4ff56083496f2b05bf249733bbcb 0.674647969000 1349176 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": 893023, "vin": [ { "gen": { "height": 893013 } } ], "vout": [ { "amount": 674647969, "target": { "key": "4a4936c66de8cfb6b06a783df0eb7caafadf4ff56083496f2b05bf249733bbcb" } } ], "extra": [ 1, 71, 137, 189, 228, 158, 139, 25, 137, 81, 218, 156, 26, 92, 219, 233, 255, 114, 50, 234, 163, 210, 194, 106, 170, 225, 186, 221, 223, 210, 192, 3, 185, 2, 17, 0, 0, 0, 1, 197, 69, 41, 96, 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