Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 639e71fafc4596cb50441fd5d1da6bf94b2acafc61d4a2b1eff7e313ff78dfa0

Tx prefix hash: 261fe91733019b5953e4a2dfbc228a11359d6873d4d4a782aded0d6b183284a2
Tx public key: e884945c6a78ab7437ec527dd67470ed9afdf30c4b14965660f9b66c83108689
Timestamp: 1728769156 Timestamp [UCT]: 2024-10-12 21:39:16 Age [y:d:h:m:s]: 00:085:13:55:28
Block: 1130259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 61176 RingCT/type: yes/0
Extra: 01e884945c6a78ab7437ec527dd67470ed9afdf30c4b14965660f9b66c83108689021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 967b03511338dc42919baf42e4e7c29a1cb4651c6dbabd1b455d86a78934a73e 0.600000000000 1613134 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": 1130269, "vin": [ { "gen": { "height": 1130259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "967b03511338dc42919baf42e4e7c29a1cb4651c6dbabd1b455d86a78934a73e" } } ], "extra": [ 1, 232, 132, 148, 92, 106, 120, 171, 116, 55, 236, 82, 125, 214, 116, 112, 237, 154, 253, 243, 12, 75, 20, 150, 86, 96, 249, 182, 108, 131, 16, 134, 137, 2, 17, 0, 0, 0, 2, 233, 20, 221, 21, 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