Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04774dfcd238e921a158f0413d60596349712e8e6291a583922a06523abb9e6f

Tx prefix hash: 506b5ee54d9d212df894c718f67b79e9b3318ce4a1b9f46c8f4cce1595416245
Tx public key: 8583eb47da1e4a9df7507ac4b49a640b264e83488b86a56ce830f622bedb1d18
Timestamp: 1702997358 Timestamp [UCT]: 2023-12-19 14:49:18 Age [y:d:h:m:s]: 01:146:22:00:34
Block: 916602 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 366159 RingCT/type: yes/0
Extra: 018583eb47da1e4a9df7507ac4b49a640b264e83488b86a56ce830f622bedb1d1802110000000ee6d27f9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 26395d091106651ccf87894256f6b376b820b2bd905c7c33aab1e24f3d731c12 0.600000000000 1374160 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": 916612, "vin": [ { "gen": { "height": 916602 } } ], "vout": [ { "amount": 600000000, "target": { "key": "26395d091106651ccf87894256f6b376b820b2bd905c7c33aab1e24f3d731c12" } } ], "extra": [ 1, 133, 131, 235, 71, 218, 30, 74, 157, 247, 80, 122, 196, 180, 154, 100, 11, 38, 78, 131, 72, 139, 134, 165, 108, 232, 48, 246, 34, 190, 219, 29, 24, 2, 17, 0, 0, 0, 14, 230, 210, 127, 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