Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e76da985340eec89625341e6f386ddf7cb2fea7bcde4a272fbc0fe4e77c4dd5b

Tx prefix hash: 7b79a895ce8c46f437946baeee2124cf37aa04fca21c35d61a20b13345ef5ee0
Tx public key: 56609a12f4e67246c7cfff6e85da196d0336d04f91b9eaf9c0e0b57e418a1142
Timestamp: 1711020961 Timestamp [UCT]: 2024-03-21 11:36:01 Age [y:d:h:m:s]: 01:016:05:36:50
Block: 983137 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 272546 RingCT/type: yes/0
Extra: 0156609a12f4e67246c7cfff6e85da196d0336d04f91b9eaf9c0e0b57e418a11420211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1aa064f46e3fae52cc6839b1292acf91855e50e13a31002064c313316e9e06a 0.600000000000 1443260 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": 983147, "vin": [ { "gen": { "height": 983137 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1aa064f46e3fae52cc6839b1292acf91855e50e13a31002064c313316e9e06a" } } ], "extra": [ 1, 86, 96, 154, 18, 244, 230, 114, 70, 199, 207, 255, 110, 133, 218, 25, 109, 3, 54, 208, 79, 145, 185, 234, 249, 192, 224, 181, 126, 65, 138, 17, 66, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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