Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d54e39c8729dfe1869d1b4b6c83ec4a005cf3ede1e6910203926609e943fc41

Tx prefix hash: 6067f7071382e6f426aee70f926db1d4793093dbf4a85b0300836dd441735d99
Tx public key: 0381e5c8a0b44f299d6bb6dba23f01b21c8b3042086fbb3b52f6821937e57a24
Timestamp: 1697373422 Timestamp [UCT]: 2023-10-15 12:37:02 Age [y:d:h:m:s]: 01:186:02:10:28
Block: 870176 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 394038 RingCT/type: yes/0
Extra: 010381e5c8a0b44f299d6bb6dba23f01b21c8b3042086fbb3b52f6821937e57a2402110000000533af99f4000000000000000000

1 output(s) for total of 0.803055779000 dcy

stealth address amount amount idx
00: 0df010b7893413d287abfaf31e747610c723d059c9933d6499fb1c90108a2b2c 0.803055779000 1325049 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": 870186, "vin": [ { "gen": { "height": 870176 } } ], "vout": [ { "amount": 803055779, "target": { "key": "0df010b7893413d287abfaf31e747610c723d059c9933d6499fb1c90108a2b2c" } } ], "extra": [ 1, 3, 129, 229, 200, 160, 180, 79, 41, 157, 107, 182, 219, 162, 63, 1, 178, 28, 139, 48, 66, 8, 111, 187, 59, 82, 246, 130, 25, 55, 229, 122, 36, 2, 17, 0, 0, 0, 5, 51, 175, 153, 244, 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