Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 27442f437f44aa98cc7007f4386fd01bb7de7e388588ef532502e59d37e6384c

Tx prefix hash: e78942fce2f8b35d8e9a7a8b6146f91343e04adf86ae63bdbd6c8469cc795ac3
Tx public key: 5d20720da80daf86b85ca0a9709f0771bef4ac32470eb5ce7765b9dd750e3f5d
Timestamp: 1710541095 Timestamp [UCT]: 2024-03-15 22:18:15 Age [y:d:h:m:s]: 01:029:17:56:34
Block: 979154 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 282236 RingCT/type: yes/0
Extra: 015d20720da80daf86b85ca0a9709f0771bef4ac32470eb5ce7765b9dd750e3f5d0211000000087a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f799e701dabbe98d0e546d69be646cf8a8b9d5271922bd05674bbaa1ca1e8b4c 0.600000000000 1439187 of 15

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": 979164, "vin": [ { "gen": { "height": 979154 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f799e701dabbe98d0e546d69be646cf8a8b9d5271922bd05674bbaa1ca1e8b4c" } } ], "extra": [ 1, 93, 32, 114, 13, 168, 13, 175, 134, 184, 92, 160, 169, 112, 159, 7, 113, 190, 244, 172, 50, 71, 14, 181, 206, 119, 101, 185, 221, 117, 14, 63, 93, 2, 17, 0, 0, 0, 8, 122, 156, 244, 199, 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