Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f912a18505308ddf9c5592cf7208fb49cfe26f7e63b27d282cd88f2d22c5cf70

Tx prefix hash: 9871b38524a06e4f69602fc522acfa7047cd62a3d0389e961bc32bff797ef2e7
Tx public key: 92db9ff65238a1f5d62bc7c963d5fe3cdf996ce661027eb33d775177f5c122aa
Timestamp: 1716711441 Timestamp [UCT]: 2024-05-26 08:17:21 Age [y:d:h:m:s]: 01:167:10:39:03
Block: 1030299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378256 RingCT/type: yes/0
Extra: 0192db9ff65238a1f5d62bc7c963d5fe3cdf996ce661027eb33d775177f5c122aa0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4d5bfeb7e958c87ebf4c73f060a732926e1d09f5227f6e525c5cafc2d34b5cc8 0.600000000000 1498554 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": 1030309, "vin": [ { "gen": { "height": 1030299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4d5bfeb7e958c87ebf4c73f060a732926e1d09f5227f6e525c5cafc2d34b5cc8" } } ], "extra": [ 1, 146, 219, 159, 246, 82, 56, 161, 245, 214, 43, 199, 201, 99, 213, 254, 60, 223, 153, 108, 230, 97, 2, 126, 179, 61, 119, 81, 119, 245, 193, 34, 170, 2, 17, 0, 0, 0, 2, 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