Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22e686a738d3623a997e22d94654046bef27ba8115a8a6b9a2b8fb116a4103af

Tx prefix hash: 55ec13cac5b4b54195688b128303af632c76fd5469e5ed1729ee430ed893aa59
Tx public key: e10ce9a2c7065c1ff37747da59562e7476e00dac7f014dc359e6c7acdd5c7079
Timestamp: 1745754394 Timestamp [UCT]: 2025-04-27 11:46:34 Age [y:d:h:m:s]: 00:240:20:46:48
Block: 1270563 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169895 RingCT/type: yes/0
Extra: 01e10ce9a2c7065c1ff37747da59562e7476e00dac7f014dc359e6c7acdd5c70790211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad9f1dbb771f632fd9d43680f0b5ba667a8ecbffee5bc91d23a8ce394164d8b3 0.600000000000 1757806 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": 1270573, "vin": [ { "gen": { "height": 1270563 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad9f1dbb771f632fd9d43680f0b5ba667a8ecbffee5bc91d23a8ce394164d8b3" } } ], "extra": [ 1, 225, 12, 233, 162, 199, 6, 92, 31, 243, 119, 71, 218, 89, 86, 46, 116, 118, 224, 13, 172, 127, 1, 77, 195, 89, 230, 199, 172, 221, 92, 112, 121, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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