Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 254368b823b4555b2b3e877f09a161ab1406b534565beaeadf9b20e6e7b5c549

Tx prefix hash: f18907abfbd320e10e8a6fdf6a1e9f419e1d26002da14b6dc32619839a6cf706
Tx public key: 8eebe9b26d14c0a946a73bc672ea1c5bf90e5e4aff9e1786ec08da212fe1e796
Timestamp: 1720932564 Timestamp [UCT]: 2024-07-14 04:49:24 Age [y:d:h:m:s]: 00:194:16:32:27
Block: 1065294 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139242 RingCT/type: yes/0
Extra: 018eebe9b26d14c0a946a73bc672ea1c5bf90e5e4aff9e1786ec08da212fe1e79602110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ae19357f7d6dc57effcb0f4e9f188b0e574c7881368a8efa24197a00e38a4fd1 0.600000000000 1535839 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": 1065304, "vin": [ { "gen": { "height": 1065294 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ae19357f7d6dc57effcb0f4e9f188b0e574c7881368a8efa24197a00e38a4fd1" } } ], "extra": [ 1, 142, 235, 233, 178, 109, 20, 192, 169, 70, 167, 59, 198, 114, 234, 28, 91, 249, 14, 94, 74, 255, 158, 23, 134, 236, 8, 218, 33, 47, 225, 231, 150, 2, 17, 0, 0, 0, 14, 145, 225, 60, 4, 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