Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 855b5505e87e3fb725b68fc419d4e214bb667b545afbfbb366f8232f21ea9d12

Tx prefix hash: 84691b91b2cb9abb40ba4c780c15a26688a098989764373cbe54c8dcdfd66dcf
Tx public key: 34c666491fb933164b39d2f387f5b8ead70f4ff328713cb6f1636ce36ef044d5
Timestamp: 1713750116 Timestamp [UCT]: 2024-04-22 01:41:56 Age [y:d:h:m:s]: 00:347:00:07:36
Block: 1005735 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 248060 RingCT/type: yes/0
Extra: 0134c666491fb933164b39d2f387f5b8ead70f4ff328713cb6f1636ce36ef044d50211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9cff17fb890e9b194751599f9a05c0468b9fd3d900e80a8633d50a51a2868889 0.600000000000 1466523 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": 1005745, "vin": [ { "gen": { "height": 1005735 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9cff17fb890e9b194751599f9a05c0468b9fd3d900e80a8633d50a51a2868889" } } ], "extra": [ 1, 52, 198, 102, 73, 31, 185, 51, 22, 75, 57, 210, 243, 135, 245, 184, 234, 215, 15, 79, 243, 40, 113, 60, 182, 241, 99, 108, 227, 110, 240, 68, 213, 2, 17, 0, 0, 0, 3, 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