Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 531841f7e11760d7cd2b8bca4177531a145ccd23bb7ec80ded153baaabd68aed

Tx prefix hash: f3460bd9e3704853d4448545b521614560d2251b7b3db059b5a1e8c05f040e3e
Tx public key: 32f6750157f6d4c00193214f8cdd83ea2f4e025ff7818697ec38f386441aaaf4
Timestamp: 1636314867 Timestamp [UCT]: 2021-11-07 19:54:27 Age [y:d:h:m:s]: 03:091:11:00:11
Block: 369497 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 843685 RingCT/type: yes/0
Extra: 0132f6750157f6d4c00193214f8cdd83ea2f4e025ff7818697ec38f386441aaaf40211000000204f792ffd000000000000000000

1 output(s) for total of 36.618744365000 dcy

stealth address amount amount idx
00: db1b57caa1cd4a832f20f7433f5d90f4b51559f2c09a18c99fa8c3caf440ac51 36.618744365000 749229 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": 369507, "vin": [ { "gen": { "height": 369497 } } ], "vout": [ { "amount": 36618744365, "target": { "key": "db1b57caa1cd4a832f20f7433f5d90f4b51559f2c09a18c99fa8c3caf440ac51" } } ], "extra": [ 1, 50, 246, 117, 1, 87, 246, 212, 192, 1, 147, 33, 79, 140, 221, 131, 234, 47, 78, 2, 95, 247, 129, 134, 151, 236, 56, 243, 134, 68, 26, 170, 244, 2, 17, 0, 0, 0, 32, 79, 121, 47, 253, 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