Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 618f7bcd8e0bb95fe4793ba44cbf66297e7c6380654565be585587ad10681d8e

Tx prefix hash: 9aa822a6367155fd06914d88eae36a912df810a33e437012ec0f1aa4f7c089a6
Tx public key: f57ebd9c74e9754a32e132b86ed47432cc2b02913265ef16075ae528531cc73b
Timestamp: 1696067156 Timestamp [UCT]: 2023-09-30 09:45:56 Age [y:d:h:m:s]: 01:192:17:58:39
Block: 859342 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 398818 RingCT/type: yes/0
Extra: 01f57ebd9c74e9754a32e132b86ed47432cc2b02913265ef16075ae528531cc73b0211000000084b8f5122000000000000000000

1 output(s) for total of 0.872254597000 dcy

stealth address amount amount idx
00: 8a7c54ba2a4a6f0e53f960fc8f99a031306cac8dad419a3d592c0adfc7760699 0.872254597000 1313564 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": 859352, "vin": [ { "gen": { "height": 859342 } } ], "vout": [ { "amount": 872254597, "target": { "key": "8a7c54ba2a4a6f0e53f960fc8f99a031306cac8dad419a3d592c0adfc7760699" } } ], "extra": [ 1, 245, 126, 189, 156, 116, 233, 117, 74, 50, 225, 50, 184, 110, 212, 116, 50, 204, 43, 2, 145, 50, 101, 239, 22, 7, 90, 229, 40, 83, 28, 199, 59, 2, 17, 0, 0, 0, 8, 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