Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0e5afa1ccf8c984b661958742c9cac2ed4723a4aad4cbb7a72a83b1b697b47dc

Tx prefix hash: 5f250f9aecfa3448a3e031bf2faf46a491bf4939f3412dd8e9506745761d48a2
Tx public key: 0e44cc8717dff7cf2aae5830c49a21e4fe0296347d8a27d21664f528903e151c
Timestamp: 1694055133 Timestamp [UCT]: 2023-09-07 02:52:13 Age [y:d:h:m:s]: 01:229:07:11:15
Block: 842636 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 425000 RingCT/type: yes/0
Extra: 010e44cc8717dff7cf2aae5830c49a21e4fe0296347d8a27d21664f528903e151c02110000000be6d27f9c000000000000000000

1 output(s) for total of 0.990825567000 dcy

stealth address amount amount idx
00: c27306f5d678e4594e754bdbc7d434296e186e9e0af108efff57273a8f57f700 0.990825567000 1295776 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": 842646, "vin": [ { "gen": { "height": 842636 } } ], "vout": [ { "amount": 990825567, "target": { "key": "c27306f5d678e4594e754bdbc7d434296e186e9e0af108efff57273a8f57f700" } } ], "extra": [ 1, 14, 68, 204, 135, 23, 223, 247, 207, 42, 174, 88, 48, 196, 154, 33, 228, 254, 2, 150, 52, 125, 138, 39, 210, 22, 100, 245, 40, 144, 62, 21, 28, 2, 17, 0, 0, 0, 11, 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