Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afd73225fc4bfda112a9c9ce44accc34e29f97dd5aba0612c069062860a481ec

Tx prefix hash: 2a1034d5d315b4f291cee87b0434ac4b3e570ac9ccd1700d53126270579222d6
Tx public key: 6f668f8c857d97ed3b3a9f47cb7fe8f79f1ffaa4e58cac77a83f28a85495bff1
Timestamp: 1672575369 Timestamp [UCT]: 2023-01-01 12:16:09 Age [y:d:h:m:s]: 02:017:11:01:48
Block: 665246 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 534387 RingCT/type: yes/0
Extra: 016f668f8c857d97ed3b3a9f47cb7fe8f79f1ffaa4e58cac77a83f28a85495bff102110000000152542ceb000000000000000000

1 output(s) for total of 3.834986235000 dcy

stealth address amount amount idx
00: a07aa900e2fa0bc162dc64e8bc2124d12158e9041617cf787e18b2f742902792 3.834986235000 1106269 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": 665256, "vin": [ { "gen": { "height": 665246 } } ], "vout": [ { "amount": 3834986235, "target": { "key": "a07aa900e2fa0bc162dc64e8bc2124d12158e9041617cf787e18b2f742902792" } } ], "extra": [ 1, 111, 102, 143, 140, 133, 125, 151, 237, 59, 58, 159, 71, 203, 127, 232, 247, 159, 31, 250, 164, 229, 140, 172, 119, 168, 63, 40, 168, 84, 149, 191, 241, 2, 17, 0, 0, 0, 1, 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