Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e30fe35b092eabce32a15f871fd6b619cb26119e20ae58160e804a1e865a5fe

Tx prefix hash: c08f1f395e29fcab2e561cf44b3a10006cdf1fc5133ce55d6891c10031b2135b
Tx public key: 07e3fa7401e0eb8e7c8ecc7dc1bf01fb4348122bb8f3a216e92df375ac27904d
Timestamp: 1672856362 Timestamp [UCT]: 2023-01-04 18:19:22 Age [y:d:h:m:s]: 02:091:09:39:37
Block: 667579 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 587002 RingCT/type: yes/0
Extra: 0107e3fa7401e0eb8e7c8ecc7dc1bf01fb4348122bb8f3a216e92df375ac27904d02110000000252542ceb000000000000000000

1 output(s) for total of 3.767329519000 dcy

stealth address amount amount idx
00: f0cf07954b2500e28223cebe27ef5eb113ab9a246e81368699edd1a406374342 3.767329519000 1108792 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": 667589, "vin": [ { "gen": { "height": 667579 } } ], "vout": [ { "amount": 3767329519, "target": { "key": "f0cf07954b2500e28223cebe27ef5eb113ab9a246e81368699edd1a406374342" } } ], "extra": [ 1, 7, 227, 250, 116, 1, 224, 235, 142, 124, 142, 204, 125, 193, 191, 1, 251, 67, 72, 18, 43, 184, 243, 162, 22, 233, 45, 243, 117, 172, 39, 144, 77, 2, 17, 0, 0, 0, 2, 82, 84, 44, 235, 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