Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5c5e191bd668e2a3e1182b38bfe9a10765df766f6a4a997f948a5d488691d54f

Tx prefix hash: 60bed199c388a6f935adb21150ab44d99b2a4bffa3b23d735986603b70df6d78
Tx public key: 035b2ed33845a5ef4e960b441aba0ffe482c20e162a682236437f6a8f3735cb8
Timestamp: 1707177392 Timestamp [UCT]: 2024-02-05 23:56:32 Age [y:d:h:m:s]: 01:058:19:31:43
Block: 951241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303089 RingCT/type: yes/0
Extra: 01035b2ed33845a5ef4e960b441aba0ffe482c20e162a682236437f6a8f3735cb80211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e444723c4d84f87fc5ac4cde026691aab6717649d6e620afca69c49c1f9ec887 0.600000000000 1409981 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": 951251, "vin": [ { "gen": { "height": 951241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e444723c4d84f87fc5ac4cde026691aab6717649d6e620afca69c49c1f9ec887" } } ], "extra": [ 1, 3, 91, 46, 211, 56, 69, 165, 239, 78, 150, 11, 68, 26, 186, 15, 254, 72, 44, 32, 225, 98, 166, 130, 35, 100, 55, 246, 168, 243, 115, 92, 184, 2, 17, 0, 0, 0, 1, 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