Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3ffbf68e67746153bf20b2ec8e86460b4a488a9a5afa21902826e576d9d70dd2

Tx prefix hash: 17ffa855b7d380a9b81ed9d87c8e98100d02dcd0de8a67bc8e0d307c36144f7a
Tx public key: e9ae4018e9e4562c2a80552ddfac2c1e2460a9b721548683362b022245ba219c
Timestamp: 1737624579 Timestamp [UCT]: 2025-01-23 09:29:39 Age [y:d:h:m:s]: 00:147:13:22:30
Block: 1203472 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105184 RingCT/type: yes/0
Extra: 01e9ae4018e9e4562c2a80552ddfac2c1e2460a9b721548683362b022245ba219c0211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6c3358994fecfd8f9639a82d26518b67cdd2163ef1bd214d6a9ee4f16fb347af 0.600000000000 1690149 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": 1203482, "vin": [ { "gen": { "height": 1203472 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6c3358994fecfd8f9639a82d26518b67cdd2163ef1bd214d6a9ee4f16fb347af" } } ], "extra": [ 1, 233, 174, 64, 24, 233, 228, 86, 44, 42, 128, 85, 45, 223, 172, 44, 30, 36, 96, 169, 183, 33, 84, 134, 131, 54, 43, 2, 34, 69, 186, 33, 156, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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