Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 965eddc1b3c00b77119546a69181ef2a4ee09c2a46090425ceab7b30c450819b

Tx prefix hash: c45d6fd4cc1dba64ed2cbfcad354eb2b1a46f478ed74ac6f6d6deca55b6b03a6
Tx public key: 715bcfef663a24813a7ad5f4eb6ad200acd8efa0669922520c4a9607be689578
Timestamp: 1688220833 Timestamp [UCT]: 2023-07-01 14:13:53 Age [y:d:h:m:s]: 01:198:16:21:15
Block: 794353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 403358 RingCT/type: yes/0
Extra: 01715bcfef663a24813a7ad5f4eb6ad200acd8efa0669922520c4a9607be6895780211000000034b8f5122000000000000000000

1 output(s) for total of 1.432118311000 dcy

stealth address amount amount idx
00: bf8bbf1869f21ebf4775357bf1a4e2f32a315bb2dcf11c16363d9975b1dc0c76 1.432118311000 1245092 of 0

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": 794363, "vin": [ { "gen": { "height": 794353 } } ], "vout": [ { "amount": 1432118311, "target": { "key": "bf8bbf1869f21ebf4775357bf1a4e2f32a315bb2dcf11c16363d9975b1dc0c76" } } ], "extra": [ 1, 113, 91, 207, 239, 102, 58, 36, 129, 58, 122, 213, 244, 235, 106, 210, 0, 172, 216, 239, 160, 102, 153, 34, 82, 12, 74, 150, 7, 190, 104, 149, 120, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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