Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59880f5bbd9f46de0e54f6e478cdaf5881d6dd57ec71094bbc9ca927b1b1ae1d

Tx prefix hash: 1c9d0caccdaef7a09730e766bb61059806a3bb65e421c5244d0eeebfcdbfe2d4
Tx public key: 2bc6d478cef2bda86dc75166013fdcb743aeda941be85fe4e66f318b7811799a
Timestamp: 1716606813 Timestamp [UCT]: 2024-05-25 03:13:33 Age [y:d:h:m:s]: 00:343:23:23:50
Block: 1029428 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245857 RingCT/type: yes/0
Extra: 012bc6d478cef2bda86dc75166013fdcb743aeda941be85fe4e66f318b7811799a02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: caab88814ae4ed9c6b3f37ea3100941673063eb4f0bc77214e7398e6121f471f 0.600000000000 1497519 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": 1029438, "vin": [ { "gen": { "height": 1029428 } } ], "vout": [ { "amount": 600000000, "target": { "key": "caab88814ae4ed9c6b3f37ea3100941673063eb4f0bc77214e7398e6121f471f" } } ], "extra": [ 1, 43, 198, 212, 120, 206, 242, 189, 168, 109, 199, 81, 102, 1, 63, 220, 183, 67, 174, 218, 148, 27, 232, 95, 228, 230, 111, 49, 139, 120, 17, 121, 154, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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