Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 65fa25af1f3581e8e1d161688286a663f8eb254249f103ed30eec5b7b975ceb9

Tx prefix hash: b29748b089db1d347d787ffa08477e8db0739010edb0feac633a55ccc9e8d20a
Tx public key: 8d28ea9c4eeee57d1ba50adfc52869f44ce195af8f1b65bdb4e2a2eb23880457
Timestamp: 1580678156 Timestamp [UCT]: 2020-02-02 21:15:56 Age [y:d:h:m:s]: 04:298:04:39:04
Block: 57237 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104568 RingCT/type: yes/0
Extra: 018d28ea9c4eeee57d1ba50adfc52869f44ce195af8f1b65bdb4e2a2eb238804570211000000acbd0f9f9f000000000000000000

1 output(s) for total of 396.605180026000 dcy

stealth address amount amount idx
00: 4373306cee2bb6eaf2bb28be807a4d3d695c5d870ff024e1fdf412c907842aad 396.605180026000 105654 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": 57247, "vin": [ { "gen": { "height": 57237 } } ], "vout": [ { "amount": 396605180026, "target": { "key": "4373306cee2bb6eaf2bb28be807a4d3d695c5d870ff024e1fdf412c907842aad" } } ], "extra": [ 1, 141, 40, 234, 156, 78, 238, 229, 125, 27, 165, 10, 223, 197, 40, 105, 244, 76, 225, 149, 175, 143, 27, 101, 189, 180, 226, 162, 235, 35, 136, 4, 87, 2, 17, 0, 0, 0, 172, 189, 15, 159, 159, 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