Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9945433f35fa5859247d63f8ee8b0f94cf0cc94ff8d809a7d82d040d565ac3c2

Tx prefix hash: 92402229687da6df762bfc2ca422a5cc77db6f070faa4d53080ea64b88e4f892
Tx public key: af7438f4ee8259e43d21cc2e103401ee1253d0fc5ab4cb7c364c1fc99b9fa13e
Timestamp: 1709222612 Timestamp [UCT]: 2024-02-29 16:03:32 Age [y:d:h:m:s]: 01:251:05:36:20
Block: 968209 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 438271 RingCT/type: yes/0
Extra: 01af7438f4ee8259e43d21cc2e103401ee1253d0fc5ab4cb7c364c1fc99b9fa13e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 71c6a85902fe5b164856fd710750648506cc04d34761aa2398e6310ed6c36caf 0.600000000000 1428010 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": 968219, "vin": [ { "gen": { "height": 968209 } } ], "vout": [ { "amount": 600000000, "target": { "key": "71c6a85902fe5b164856fd710750648506cc04d34761aa2398e6310ed6c36caf" } } ], "extra": [ 1, 175, 116, 56, 244, 238, 130, 89, 228, 61, 33, 204, 46, 16, 52, 1, 238, 18, 83, 208, 252, 90, 180, 203, 124, 54, 76, 31, 201, 155, 159, 161, 62, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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