Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c81c7141394775e2c36b02556a01445ccad350cd23b8f5235bed591d2c892f7

Tx prefix hash: ae879d051feca7c4f306609f439819eec589999ebefd53513b53d84ae8d4030b
Tx public key: 88e13f575531fca1bdc1844ec9893a6e0bf3a228ac623f97a0c3125f4cba7a0f
Timestamp: 1705409011 Timestamp [UCT]: 2024-01-16 12:43:31 Age [y:d:h:m:s]: 01:149:22:04:18
Block: 936561 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 368229 RingCT/type: yes/0
Extra: 0188e13f575531fca1bdc1844ec9893a6e0bf3a228ac623f97a0c3125f4cba7a0f0211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ceefb566683b4462a1d411b2cb737841604f7a64219cceb6707d1fd3b8a07a43 0.600000000000 1394589 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": 936571, "vin": [ { "gen": { "height": 936561 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ceefb566683b4462a1d411b2cb737841604f7a64219cceb6707d1fd3b8a07a43" } } ], "extra": [ 1, 136, 225, 63, 87, 85, 49, 252, 161, 189, 193, 132, 78, 201, 137, 58, 110, 11, 243, 162, 40, 172, 98, 63, 151, 160, 195, 18, 95, 76, 186, 122, 15, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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