Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 363b42e878e9d081580632b2d672c4d52b0aab3d84146c5d4c4d2e1743bf57f6

Tx prefix hash: 773799b4dd440987b6ffa4762af9ff00ffa64e4642e0b094bc714926e87f8298
Tx public key: c6d5e3d7d2fce8d547f357dfb01eefac3084068d516f6acdb4e06e3f9a381714
Timestamp: 1751583281 Timestamp [UCT]: 2025-07-03 22:54:41 Age [y:d:h:m:s]: 00:184:11:52:13
Block: 1318235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 130193 RingCT/type: yes/0
Extra: 01c6d5e3d7d2fce8d547f357dfb01eefac3084068d516f6acdb4e06e3f9a3817140211000000012609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4b1e080be181bdbadc71c39523658cb16ebcca599227946b6011c1e96c157766 0.600000000000 1805912 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": 1318245, "vin": [ { "gen": { "height": 1318235 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4b1e080be181bdbadc71c39523658cb16ebcca599227946b6011c1e96c157766" } } ], "extra": [ 1, 198, 213, 227, 215, 210, 252, 232, 213, 71, 243, 87, 223, 176, 30, 239, 172, 48, 132, 6, 141, 81, 111, 106, 205, 180, 224, 110, 63, 154, 56, 23, 20, 2, 17, 0, 0, 0, 1, 38, 9, 179, 160, 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