Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 280e7ea866a3bcf5cb610cbeafdb71d00954b5fad6a4385fcf6c13de4b56d915

Tx prefix hash: 21084500f131d780eeb0a1bde6a3b50ae130511276f71fad373cadc5f0ec2541
Tx public key: eb5e1f6bd984e6db701db90fdd5c10d31f769705dc638f8607e8599c865e2870
Timestamp: 1702336206 Timestamp [UCT]: 2023-12-11 23:10:06 Age [y:d:h:m:s]: 01:174:02:39:43
Block: 911125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 385606 RingCT/type: yes/0
Extra: 01eb5e1f6bd984e6db701db90fdd5c10d31f769705dc638f8607e8599c865e287002110000000675e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a1e7abae6b12c3a1241c4597e18e7e18799b07ee1d65db5f1fae077ba4086f73 0.600000000000 1368304 of 15

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": 911135, "vin": [ { "gen": { "height": 911125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a1e7abae6b12c3a1241c4597e18e7e18799b07ee1d65db5f1fae077ba4086f73" } } ], "extra": [ 1, 235, 94, 31, 107, 217, 132, 230, 219, 112, 29, 185, 15, 221, 92, 16, 211, 31, 118, 151, 5, 220, 99, 143, 134, 7, 232, 89, 156, 134, 94, 40, 112, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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