Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 267ca24a7e873724876d97fa36150a6f1268746a1e4878fbc684e078c9d5c270

Tx prefix hash: c99cc5121e1792e9a8cf7dcc0c049657db1dd565587653878214aa99e622f6b1
Tx public key: a9d16153c7b556325bb12313d6a90cc2d691ed76d8f64c2b56c5206e870d8c42
Timestamp: 1710569884 Timestamp [UCT]: 2024-03-16 06:18:04 Age [y:d:h:m:s]: 01:017:02:45:41
Block: 979401 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 273181 RingCT/type: yes/0
Extra: 01a9d16153c7b556325bb12313d6a90cc2d691ed76d8f64c2b56c5206e870d8c420211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0be5fdc02b98c59b2ab0c2969c501834f8b81da4fcd16a0598bab42a63930574 0.600000000000 1439434 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": 979411, "vin": [ { "gen": { "height": 979401 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0be5fdc02b98c59b2ab0c2969c501834f8b81da4fcd16a0598bab42a63930574" } } ], "extra": [ 1, 169, 209, 97, 83, 199, 181, 86, 50, 91, 177, 35, 19, 214, 169, 12, 194, 214, 145, 237, 118, 216, 246, 76, 43, 86, 197, 32, 110, 135, 13, 140, 66, 2, 17, 0, 0, 0, 1, 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