Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fca96c633e1b7bb2a818ce186a37c39e6303eae3f51c0487f0b68f2819743671

Tx prefix hash: e4bbdf024a71f36a1c685d9ae1a338b6f0f93a87500d99c8391b1c30cd1fae62
Tx public key: 228d743948ba6bad0e344f8510ab2360ddb06c2c0ccabfc176a1e3edc2104c82
Timestamp: 1731768033 Timestamp [UCT]: 2024-11-16 14:40:33 Age [y:d:h:m:s]: 00:135:07:33:32
Block: 1155023 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 96530 RingCT/type: yes/0
Extra: 01228d743948ba6bad0e344f8510ab2360ddb06c2c0ccabfc176a1e3edc2104c82021100000002dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0f0af95fd573a16ae215e94b6063450a68bad2f409e5d295de2c272651364581 0.600000000000 1640636 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": 1155033, "vin": [ { "gen": { "height": 1155023 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0f0af95fd573a16ae215e94b6063450a68bad2f409e5d295de2c272651364581" } } ], "extra": [ 1, 34, 141, 116, 57, 72, 186, 107, 173, 14, 52, 79, 133, 16, 171, 35, 96, 221, 176, 108, 44, 12, 202, 191, 193, 118, 161, 227, 237, 194, 16, 76, 130, 2, 17, 0, 0, 0, 2, 223, 195, 186, 73, 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