Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 889a8d406c1c185a4d2134c15568da6e7c5a80e6e189d15df4c30564b575bd6c

Tx prefix hash: bcb98e2fceb6140f9089d5cd1ceaa22b3d8bd9d891c0bec82d41d08127cca64a
Tx public key: 9d85e9c1f0028813ac7ee5dc94327c3049d56333a31dc406db10d5b1d99a3f78
Timestamp: 1653471549 Timestamp [UCT]: 2022-05-25 09:39:09 Age [y:d:h:m:s]: 02:192:10:47:34
Block: 508512 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 658147 RingCT/type: yes/0
Extra: 019d85e9c1f0028813ac7ee5dc94327c3049d56333a31dc406db10d5b1d99a3f78021100000004faf35c9c000000000000000000

1 output(s) for total of 12.679112161000 dcy

stealth address amount amount idx
00: a1af284f7809211d99a69da67a32c8a6bb939a580c9fa68b8198db21ec5844fd 12.679112161000 934443 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": 508522, "vin": [ { "gen": { "height": 508512 } } ], "vout": [ { "amount": 12679112161, "target": { "key": "a1af284f7809211d99a69da67a32c8a6bb939a580c9fa68b8198db21ec5844fd" } } ], "extra": [ 1, 157, 133, 233, 193, 240, 2, 136, 19, 172, 126, 229, 220, 148, 50, 124, 48, 73, 213, 99, 51, 163, 29, 196, 6, 219, 16, 213, 177, 217, 154, 63, 120, 2, 17, 0, 0, 0, 4, 250, 243, 92, 156, 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