Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1f9cf9f6c8baa662c44ffb6939fe9bdad7fb8388ae9536b6a580340fd02f8bf

Tx prefix hash: e1054b06dc4408ac5959d0f71fde48d106088b104ec13996beaa03ef7f874b1c
Tx public key: b79ffb845f5e20c0457cf7b7d26859409e19c7b68e0db96f72fcbacca24a72cc
Timestamp: 1731176959 Timestamp [UCT]: 2024-11-09 18:29:19 Age [y:d:h:m:s]: 00:130:19:01:14
Block: 1150135 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 93320 RingCT/type: yes/0
Extra: 01b79ffb845f5e20c0457cf7b7d26859409e19c7b68e0db96f72fcbacca24a72cc021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 863d5faf85433159db13f2a3326796fc9e8498e612de61e75329703fab48e97b 0.600000000000 1635352 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": 1150145, "vin": [ { "gen": { "height": 1150135 } } ], "vout": [ { "amount": 600000000, "target": { "key": "863d5faf85433159db13f2a3326796fc9e8498e612de61e75329703fab48e97b" } } ], "extra": [ 1, 183, 159, 251, 132, 95, 94, 32, 192, 69, 124, 247, 183, 210, 104, 89, 64, 158, 25, 199, 182, 142, 13, 185, 111, 114, 252, 186, 204, 162, 74, 114, 204, 2, 17, 0, 0, 0, 1, 0, 127, 151, 138, 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