Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 32fdf4eccc2b44644897207dbc5e893097b51405102083828432e1929b3bf1fb

Tx prefix hash: 17c9c74793be92d89d797fd6ae4b1da697a1abb5a4873579d03a239d36741c85
Tx public key: d95e4f657f92f44b57d7ee31baaadbaa9ea1cec0f8b5f7c216bfcbbc7ba987ab
Timestamp: 1730352630 Timestamp [UCT]: 2024-10-31 05:30:30 Age [y:d:h:m:s]: 00:178:07:54:59
Block: 1143301 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 127309 RingCT/type: yes/0
Extra: 01d95e4f657f92f44b57d7ee31baaadbaa9ea1cec0f8b5f7c216bfcbbc7ba987ab021100000001dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b7419c613e4b1c8aa8fd57ae890b770e196d167fb04630e4afd7d4284919adb1 0.600000000000 1627164 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": 1143311, "vin": [ { "gen": { "height": 1143301 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b7419c613e4b1c8aa8fd57ae890b770e196d167fb04630e4afd7d4284919adb1" } } ], "extra": [ 1, 217, 94, 79, 101, 127, 146, 244, 75, 87, 215, 238, 49, 186, 170, 219, 170, 158, 161, 206, 192, 248, 181, 247, 194, 22, 191, 203, 188, 123, 169, 135, 171, 2, 17, 0, 0, 0, 1, 223, 195, 186, 73, 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