Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b640aedd55c54831fbc7b182ea8eecd4d0c920fef3ea7fdfd667620b58af0baf

Tx prefix hash: b64c56ce7447f605ee2f86dd41767041c192f2c93c8d2cc311d5df945fa7b576
Tx public key: fd2775f9c0988151d372566047186bc343ef4462151cbf9f224f82a042593230
Timestamp: 1656950558 Timestamp [UCT]: 2022-07-04 16:02:38 Age [y:d:h:m:s]: 03:119:13:46:06
Block: 536569 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 865165 RingCT/type: yes/0
Extra: 01fd2775f9c0988151d372566047186bc343ef4462151cbf9f224f82a042593230021100000013cb8520c2000000000000000000

1 output(s) for total of 10.235859466000 dcy

stealth address amount amount idx
00: 4e69c4ea6544ffb98b9609a2fccaa2cccdb652cc6fd7c0f91b63e2e328302353 10.235859466000 966346 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": 536579, "vin": [ { "gen": { "height": 536569 } } ], "vout": [ { "amount": 10235859466, "target": { "key": "4e69c4ea6544ffb98b9609a2fccaa2cccdb652cc6fd7c0f91b63e2e328302353" } } ], "extra": [ 1, 253, 39, 117, 249, 192, 152, 129, 81, 211, 114, 86, 96, 71, 24, 107, 195, 67, 239, 68, 98, 21, 28, 191, 159, 34, 79, 130, 160, 66, 89, 50, 48, 2, 17, 0, 0, 0, 19, 203, 133, 32, 194, 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