Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0f430b4dbb2c415b288bf1241d9712cd049dc4d13355241c4d01b02375394c0a

Tx prefix hash: 7e752e4a26d45a8d9beb6a3d41a0a8cca2fc4352c2af31eb783addff5b4fdb47
Tx public key: 33e9a6a2effc5c5dd2c50d8ff5fd32776bc1820156ccfd092672c6875c3be5a9
Timestamp: 1694137007 Timestamp [UCT]: 2023-09-08 01:36:47 Age [y:d:h:m:s]: 01:265:10:43:49
Block: 843328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 450859 RingCT/type: yes/0
Extra: 0133e9a6a2effc5c5dd2c50d8ff5fd32776bc1820156ccfd092672c6875c3be5a90211000000384b8f5122000000000000000000

1 output(s) for total of 0.985608228000 dcy

stealth address amount amount idx
00: 835a86391f47d966803ad0bc4b104264e20fa80b6e1c0f72fdc4d7b46e260f67 0.985608228000 1296548 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": 843338, "vin": [ { "gen": { "height": 843328 } } ], "vout": [ { "amount": 985608228, "target": { "key": "835a86391f47d966803ad0bc4b104264e20fa80b6e1c0f72fdc4d7b46e260f67" } } ], "extra": [ 1, 51, 233, 166, 162, 239, 252, 92, 93, 210, 197, 13, 143, 245, 253, 50, 119, 107, 193, 130, 1, 86, 204, 253, 9, 38, 114, 198, 135, 92, 59, 229, 169, 2, 17, 0, 0, 0, 56, 75, 143, 81, 34, 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