Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9464619cf2eabe74d8f84a4d897fcbfa0c0c62334d3b4bcbec9ad82d11ac033f

Tx prefix hash: 5b59536c7b3a86721861725a89367a0ac0cda024c1d2d76543161e0d7982a10a
Tx public key: b80917e7af6851d54e574109d9956bed7734c9e6d207fb9533379752a32af4e4
Timestamp: 1685569942 Timestamp [UCT]: 2023-05-31 21:52:22 Age [y:d:h:m:s]: 01:346:03:23:18
Block: 772370 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 508593 RingCT/type: yes/0
Extra: 01b80917e7af6851d54e574109d9956bed7734c9e6d207fb9533379752a32af4e402110000000175e3f0e9000000000000000000

1 output(s) for total of 1.693626866000 dcy

stealth address amount amount idx
00: 58aa14570f83f6c964e5a3c8e78ade2605af46be026053ab2de6c802556274c8 1.693626866000 1221771 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": 772380, "vin": [ { "gen": { "height": 772370 } } ], "vout": [ { "amount": 1693626866, "target": { "key": "58aa14570f83f6c964e5a3c8e78ade2605af46be026053ab2de6c802556274c8" } } ], "extra": [ 1, 184, 9, 23, 231, 175, 104, 81, 213, 78, 87, 65, 9, 217, 149, 107, 237, 119, 52, 201, 230, 210, 7, 251, 149, 51, 55, 151, 82, 163, 42, 244, 228, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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