Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f089f5f1a7e256f38b66f87b5d555fd60d9c83e3e75da57da7b4073ca5c5a9cb

Tx prefix hash: 2a891567d28d67b340a8e1510ed48ddc8b978a7c6a654f4ca8caf98925b2cb8c
Tx public key: 5a8c51dcfe56ed8c19769e800ece5622890fa562565f4ea6f32ed1173e110ffa
Timestamp: 1722916541 Timestamp [UCT]: 2024-08-06 03:55:41 Age [y:d:h:m:s]: 00:246:01:21:26
Block: 1081728 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175751 RingCT/type: yes/0
Extra: 015a8c51dcfe56ed8c19769e800ece5622890fa562565f4ea6f32ed1173e110ffa021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3b79415fc06adb8785fb4aaa3392bec9b9d38e7c6897c5483002f94d0003a805 0.600000000000 1555549 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": 1081738, "vin": [ { "gen": { "height": 1081728 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3b79415fc06adb8785fb4aaa3392bec9b9d38e7c6897c5483002f94d0003a805" } } ], "extra": [ 1, 90, 140, 81, 220, 254, 86, 237, 140, 25, 118, 158, 128, 14, 206, 86, 34, 137, 15, 165, 98, 86, 95, 78, 166, 243, 46, 209, 23, 62, 17, 15, 250, 2, 17, 0, 0, 0, 7, 233, 20, 221, 21, 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