Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f08ec42631a5266e72d1c6e6986e4ca7a7e4c83846b02160c50cf02be72e5d7a

Tx prefix hash: e0fd3ec5991f35bc7544b9777902a29dbdfb4f70ddffa9b393f3e60a6c102034
Tx public key: fe4aedc5474a6efc6e56bbc37f46007027fce0f07b6d8570a5c16a5cfe42f1a3
Timestamp: 1723830370 Timestamp [UCT]: 2024-08-16 17:46:10 Age [y:d:h:m:s]: 00:145:14:37:26
Block: 1089312 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104157 RingCT/type: yes/0
Extra: 01fe4aedc5474a6efc6e56bbc37f46007027fce0f07b6d8570a5c16a5cfe42f1a3021100000004e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a7efb350391a46fe9316160b552d996d74e7a4881abbac2523223e668195eba 0.600000000000 1563931 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": 1089322, "vin": [ { "gen": { "height": 1089312 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a7efb350391a46fe9316160b552d996d74e7a4881abbac2523223e668195eba" } } ], "extra": [ 1, 254, 74, 237, 197, 71, 74, 110, 252, 110, 86, 187, 195, 127, 70, 0, 112, 39, 252, 224, 240, 123, 109, 133, 112, 165, 193, 106, 92, 254, 66, 241, 163, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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