Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7528aa3225e22bcaca4ce9d9d45e3c4108176b80b3656f994c7ebf0b165f29d4

Tx prefix hash: 78b6dd7c329d81b5f6e7d3fa81c9579f3f08030dd99fe7d5df6f9f0b21e4ad2f
Tx public key: 7bb58cec89312b7db20414cb06080a60c9ad0dfdbc8426cac3f86ab666100da9
Timestamp: 1632422611 Timestamp [UCT]: 2021-09-23 18:43:31 Age [y:d:h:m:s]: 03:232:06:17:32
Block: 339577 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 942097 RingCT/type: yes/0
Extra: 017bb58cec89312b7db20414cb06080a60c9ad0dfdbc8426cac3f86ab666100da9021100000006a272b9cb000000000000000000

1 output(s) for total of 46.008795814000 dcy

stealth address amount amount idx
00: 49f6aa4f7e1d7d61457940e767771695ef09f74a2262d0f712d6118b39b4b644 46.008795814000 698348 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": 339587, "vin": [ { "gen": { "height": 339577 } } ], "vout": [ { "amount": 46008795814, "target": { "key": "49f6aa4f7e1d7d61457940e767771695ef09f74a2262d0f712d6118b39b4b644" } } ], "extra": [ 1, 123, 181, 140, 236, 137, 49, 43, 125, 178, 4, 20, 203, 6, 8, 10, 96, 201, 173, 13, 253, 188, 132, 38, 202, 195, 248, 106, 182, 102, 16, 13, 169, 2, 17, 0, 0, 0, 6, 162, 114, 185, 203, 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