Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 63ab9adcc56b4eff3e5703844ca38d798c053df7997c5c40df18d22f55ebd2b7

Tx prefix hash: a628c268c5e3bc2511b77f0a416a1356bda661c6336aacfc660fc6c6efc701ed
Tx public key: f97270b22c0f8274f7f7fa613ad26f2951a4fa0e10dcd3c0fb9228edbf433c0f
Timestamp: 1711462095 Timestamp [UCT]: 2024-03-26 14:08:15 Age [y:d:h:m:s]: 00:233:20:40:21
Block: 986796 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 167401 RingCT/type: yes/0
Extra: 01f97270b22c0f8274f7f7fa613ad26f2951a4fa0e10dcd3c0fb9228edbf433c0f02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 33cc0301304f98b68fbbf6f6064cb16ec40c0fed51467e46889ec6ddadbc8e0c 0.600000000000 1447031 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": 986806, "vin": [ { "gen": { "height": 986796 } } ], "vout": [ { "amount": 600000000, "target": { "key": "33cc0301304f98b68fbbf6f6064cb16ec40c0fed51467e46889ec6ddadbc8e0c" } } ], "extra": [ 1, 249, 114, 112, 178, 44, 15, 130, 116, 247, 247, 250, 97, 58, 210, 111, 41, 81, 164, 250, 14, 16, 220, 211, 192, 251, 146, 40, 237, 191, 67, 60, 15, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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