Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 357c50c4f037041b26b72e0b9641773104f7123162c0557ca2440a4e04deaec7

Tx prefix hash: 9068b7c3d1928c0ef4047279249bc275719b3bd509be20e2f1525a8f9b837d1b
Tx public key: 8ffd74e9e258f3a33424ce57d601ca172031d3989806e7018d65f15bc8a2fbd6
Timestamp: 1704718816 Timestamp [UCT]: 2024-01-08 13:00:16 Age [y:d:h:m:s]: 01:085:11:28:05
Block: 930847 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 322187 RingCT/type: yes/0
Extra: 018ffd74e9e258f3a33424ce57d601ca172031d3989806e7018d65f15bc8a2fbd60211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53ea798f25004355ac62edb36b6b248557a994bb36c76ae7da46d2e602ba9765 0.600000000000 1388737 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": 930857, "vin": [ { "gen": { "height": 930847 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53ea798f25004355ac62edb36b6b248557a994bb36c76ae7da46d2e602ba9765" } } ], "extra": [ 1, 143, 253, 116, 233, 226, 88, 243, 163, 52, 36, 206, 87, 214, 1, 202, 23, 32, 49, 211, 152, 152, 6, 231, 1, 141, 101, 241, 91, 200, 162, 251, 214, 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