Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7cb7afa31b1ecf25f64c6e5c732393131bb4dd2a9fe59990e851094eb3bfa22

Tx prefix hash: 8d0765772f61870db9563dc50f8871d320309d92f024e94b212ef0251ee92a1a
Tx public key: 478cbefb76ac61a57cbd8ef8e86eb5361a024cbd5680fa098f2a0ae26ff32752
Timestamp: 1702231125 Timestamp [UCT]: 2023-12-10 17:58:45 Age [y:d:h:m:s]: 01:036:22:07:59
Block: 910247 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 287737 RingCT/type: yes/0
Extra: 01478cbefb76ac61a57cbd8ef8e86eb5361a024cbd5680fa098f2a0ae26ff32752021100000003faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beb9d4f59c4413037733458c7b4b707c10ac3a567914e8c65180a9fef330f945 0.600000000000 1367392 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": 910257, "vin": [ { "gen": { "height": 910247 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beb9d4f59c4413037733458c7b4b707c10ac3a567914e8c65180a9fef330f945" } } ], "extra": [ 1, 71, 140, 190, 251, 118, 172, 97, 165, 124, 189, 142, 248, 232, 110, 181, 54, 26, 2, 76, 189, 86, 128, 250, 9, 143, 42, 10, 226, 111, 243, 39, 82, 2, 17, 0, 0, 0, 3, 250, 243, 92, 156, 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