Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97755f8b1a82cb22acf5ca1000c23230ad491e0bb31807c3d1a5e9e5f8078007

Tx prefix hash: bf8cde815ad9f3aa8ccfec5423e47f301e9abb182f70fe85155081e24f3fad1f
Tx public key: e1068fcf6ffd6e930ccdd18659fd9281a5a16717fc152432a69b0acb73556d88
Timestamp: 1705429037 Timestamp [UCT]: 2024-01-16 18:17:17 Age [y:d:h:m:s]: 01:322:20:49:09
Block: 936736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 489625 RingCT/type: yes/0
Extra: 01e1068fcf6ffd6e930ccdd18659fd9281a5a16717fc152432a69b0acb73556d880211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e859f81667a827058eb24141b90e9aea543cc191f2d0a8195010b5b2c8f6a93 0.600000000000 1394774 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": 936746, "vin": [ { "gen": { "height": 936736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e859f81667a827058eb24141b90e9aea543cc191f2d0a8195010b5b2c8f6a93" } } ], "extra": [ 1, 225, 6, 143, 207, 111, 253, 110, 147, 12, 205, 209, 134, 89, 253, 146, 129, 165, 161, 103, 23, 252, 21, 36, 50, 166, 155, 10, 203, 115, 85, 109, 136, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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