Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a542ad85a2b330ef240559927f6834a6a1f4d8adf2ba13c22a0001c3f1c2884

Tx prefix hash: 94c74adf9e8b9b8aaabb5c90ca884768da7092cc8b86da8bbe78eea1ae7bde41
Tx public key: 665730f3343ca73147907953a0bb3983a9eaa11a94fe23ab99f7098bfb9d2fe7
Timestamp: 1715984704 Timestamp [UCT]: 2024-05-17 22:25:04 Age [y:d:h:m:s]: 00:351:07:25:56
Block: 1024268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 251110 RingCT/type: yes/0
Extra: 01665730f3343ca73147907953a0bb3983a9eaa11a94fe23ab99f7098bfb9d2fe7021100000001e08532b6000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d2165fd00974323ca3c753aa028e5ec1591f72e88f1c8a101ac77b50f77f3f7c 0.600000000000 1489877 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": 1024278, "vin": [ { "gen": { "height": 1024268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d2165fd00974323ca3c753aa028e5ec1591f72e88f1c8a101ac77b50f77f3f7c" } } ], "extra": [ 1, 102, 87, 48, 243, 52, 60, 167, 49, 71, 144, 121, 83, 160, 187, 57, 131, 169, 234, 161, 26, 148, 254, 35, 171, 153, 247, 9, 139, 251, 157, 47, 231, 2, 17, 0, 0, 0, 1, 224, 133, 50, 182, 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