Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65059af49efb105bcda0084a24d6c33fd102bfd65dc9bbb763efc900c96d986b

Tx prefix hash: 816f63f2f36b0ee643e0120157c10d96fdc21f9c707da827e51cc03c69ad7318
Tx public key: bb57c0d60f44fa66e942d96e275e6d9d1dc8ed29e1baca5f91d7a6eeab433d90
Timestamp: 1697168042 Timestamp [UCT]: 2023-10-13 03:34:02 Age [y:d:h:m:s]: 01:195:10:32:31
Block: 868464 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400739 RingCT/type: yes/0
Extra: 01bb57c0d60f44fa66e942d96e275e6d9d1dc8ed29e1baca5f91d7a6eeab433d90021100000001e6d27f9c000000000000000000

1 output(s) for total of 0.813613753000 dcy

stealth address amount amount idx
00: 6b5e0b322d1a0d1df4353da2f8ecdd1fc9a2d1ec2421728a19fcad2f647f1e68 0.813613753000 1323275 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": 868474, "vin": [ { "gen": { "height": 868464 } } ], "vout": [ { "amount": 813613753, "target": { "key": "6b5e0b322d1a0d1df4353da2f8ecdd1fc9a2d1ec2421728a19fcad2f647f1e68" } } ], "extra": [ 1, 187, 87, 192, 214, 15, 68, 250, 102, 233, 66, 217, 110, 39, 94, 109, 157, 29, 200, 237, 41, 225, 186, 202, 95, 145, 215, 166, 238, 171, 67, 61, 144, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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