Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5f98ba19dc3269b15779e3bbfde6c0f65c621ead185f1f17cc3888a111aa3888

Tx prefix hash: 06a81c23d6c815ad8c39be6e239d9c73a5dab2298fce2bc77f273a576e1e841e
Tx public key: 857e356962f76dfa958ff281da84bc060bbb009ff28efba3f9e88d2358a98ab7
Timestamp: 1696724452 Timestamp [UCT]: 2023-10-08 00:20:52 Age [y:d:h:m:s]: 01:185:06:32:48
Block: 864794 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393458 RingCT/type: yes/0
Extra: 01857e356962f76dfa958ff281da84bc060bbb009ff28efba3f9e88d2358a98ab7021100000001bfa22221000000000000000000

1 output(s) for total of 0.836716859000 dcy

stealth address amount amount idx
00: 2a8938a300c293326f53b25fcc6e926754ea0316d0da0ff94692c534a9aad671 0.836716859000 1319314 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": 864804, "vin": [ { "gen": { "height": 864794 } } ], "vout": [ { "amount": 836716859, "target": { "key": "2a8938a300c293326f53b25fcc6e926754ea0316d0da0ff94692c534a9aad671" } } ], "extra": [ 1, 133, 126, 53, 105, 98, 247, 109, 250, 149, 143, 242, 129, 218, 132, 188, 6, 11, 187, 0, 159, 242, 142, 251, 163, 249, 232, 141, 35, 88, 169, 138, 183, 2, 17, 0, 0, 0, 1, 191, 162, 34, 33, 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