Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0091aaf5602734e73299b2ce1496977c11c5dab8c29451e76d655baf7ac6d2ae

Tx prefix hash: b48766af9090f4ba57ecfb0c7cea7dac9fae5b4cb9ac1625ce19f2c180831058
Tx public key: c0eda5f182b2ff631df00a9e6e3911c8357c513484c4ad306986ac750d673957
Timestamp: 1702135098 Timestamp [UCT]: 2023-12-09 15:18:18 Age [y:d:h:m:s]: 01:100:00:27:51
Block: 909447 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 332633 RingCT/type: yes/0
Extra: 01c0eda5f182b2ff631df00a9e6e3911c8357c513484c4ad306986ac750d673957021100000001faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5666f66e6f6f0a3d988a0662483fdb948ab5b333769217274bbf64a97a3d164c 0.600000000000 1366534 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": 909457, "vin": [ { "gen": { "height": 909447 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5666f66e6f6f0a3d988a0662483fdb948ab5b333769217274bbf64a97a3d164c" } } ], "extra": [ 1, 192, 237, 165, 241, 130, 178, 255, 99, 29, 240, 10, 158, 110, 57, 17, 200, 53, 124, 81, 52, 132, 196, 173, 48, 105, 134, 172, 117, 13, 103, 57, 87, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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