Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 46442ea758e8169e56321982f4427fb828560cf6f0aef51cf3f6308708b6e5db

Tx prefix hash: 15483ba0762be3566b83ee53c2c6497f190261dec853c65ba2d5b24db009976c
Tx public key: 91e86f8f1e59671a036a21c51f46983f8f3abb2da5614a1c79aa2da96fce57bf
Timestamp: 1703164594 Timestamp [UCT]: 2023-12-21 13:16:34 Age [y:d:h:m:s]: 01:162:22:34:33
Block: 917976 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 377629 RingCT/type: yes/0
Extra: 0191e86f8f1e59671a036a21c51f46983f8f3abb2da5614a1c79aa2da96fce57bf02110000000a7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71b896cd9dec89335d7c8ec00bc8f7adb2168369f17b3e1e82f93182aecf5512 0.600000000000 1375610 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": 917986, "vin": [ { "gen": { "height": 917976 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71b896cd9dec89335d7c8ec00bc8f7adb2168369f17b3e1e82f93182aecf5512" } } ], "extra": [ 1, 145, 232, 111, 143, 30, 89, 103, 26, 3, 106, 33, 197, 31, 70, 152, 63, 143, 58, 187, 45, 165, 97, 74, 28, 121, 170, 45, 169, 111, 206, 87, 191, 2, 17, 0, 0, 0, 10, 122, 156, 244, 199, 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