Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46a55b58df57717fbec78a83c7a9406d6e1c9d191c15df4bca31786034a30ef3

Tx prefix hash: 27807a6ddf83c251cd29e314b0d24ca6576b9bafc9eff1e288c89f18ba5d7378
Tx public key: bb611c2c92ffbb8c4876afa9b225ab542ddf045266ad920e27ab728613fd2d5f
Timestamp: 1721128334 Timestamp [UCT]: 2024-07-16 11:12:14 Age [y:d:h:m:s]: 00:131:16:22:33
Block: 1066930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 94205 RingCT/type: yes/0
Extra: 01bb611c2c92ffbb8c4876afa9b225ab542ddf045266ad920e27ab728613fd2d5f02110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: af49be1c7d09d3b4ab842a07daf2d1c3946618dc4faf603bd4adc40c13dccbf2 0.600000000000 1537609 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": 1066940, "vin": [ { "gen": { "height": 1066930 } } ], "vout": [ { "amount": 600000000, "target": { "key": "af49be1c7d09d3b4ab842a07daf2d1c3946618dc4faf603bd4adc40c13dccbf2" } } ], "extra": [ 1, 187, 97, 28, 44, 146, 255, 187, 140, 72, 118, 175, 169, 178, 37, 171, 84, 45, 223, 4, 82, 102, 173, 146, 14, 39, 171, 114, 134, 19, 253, 45, 95, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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